System and method for creating, managing, and displaying 3d digital collectibles

ABSTRACT

A system and method for creating, managing, and displaying 3D digital collectibles comprising a virtual, three dimensional, n-sided structure including a digital media file or set of digital media files representing an event rendered on a representation of at least a first surface thereof, and data relating to the event rendered on at least a second surface thereof and other content on one or more other surfaces, where the digital media file may be video clip of the event that can be played automatically via a media player associated with the display.

This application is a continuation of U.S. patent application Ser. No.17/529,383, filed Nov. 18, 2021, is a continuation of U.S. patentapplication Ser. No. 17/229,455, filed Apr. 13, 2021, entitled “SYSTEMAND METHOD FOR CREATING, MANAGING, AND DISPLAYING 3D DIGITALCOLLECTIBLES”, each of which is hereby incorporated herein by referencein its entirety.

FIELD OF THE INVENTION

The field of the invention relates to a platform for creating, managing,and displaying 3D digital collectibles of sports plays or other events.

BACKGROUND OF THE INVENTION

Physical collectibles, such as baseball cards, are known. Recently,digital collectibles have also been developed. However, the technologyrelated to such digital collectibles is limited. For example, knowndigital collectibles are often static, two-dimensional, images. Theseand other technical limitations and drawbacks exist with knowncollectibles.

BRIEF SUMMARY OF THE INVENTION

According to an aspect of the invention, there is provided a system andmethod for creating, managing, and displaying a 3D digital collectibleincluding, a 3D digital collectible including at least one digital mediafile and associated data. A digital media file may relate to a visualrepresentation of an event during an entertainment experience, such as avideo highlight or related images, and the data may be data associatedwith the event, experience, and/or the digital media file.

According to another aspect of the invention, the 3D digital collectiblemay include a digital media file (e.g., a video file) or set of digitalmedia files, representing an event (e.g., a sports play or other eventsas detailed below), data relating to the event and/or other content. Thedigital media files, data and/or other content may be stored in a systemmemory associated with the server. The 3D digital collectible may be avirtual, three dimensional n-sided structure (where n is preferablygreater than 3), where the n-surfaces may be configured to form ann-sided 3D shape (e.g., a cube, pyramid, octagon, or other 3D shape).According to some embodiments, the 3D digital collectible includes atleast one digital media file or set of digital media files representingan event rendered on a representation of at least a first of the nsurfaces data relating to the event rendered on at least a secondsurface thereof and other content on one or more other surfaces. Eachsurface may include a combination of digital media files, data and/orother content. The digital media file may be video clip of the event ora portion thereof that can be played automatically via a media playerassociated with the display.

According to another aspect of the invention, there is provided aplatform for creating, managing and displaying 3D digital collectibles.The platform may include a computer server including a processorprogrammed with computer instructions including at least anadministration module, a display generator, a media player. The platformmay also include an associated computer memory that stores a datastructure comprising media files, associated data, and other content andan association therebetween, along with rules that define what is to bedisplayed on the 3D digital collectible, metadata relating to events andother information.

According to another aspect of the invention, the platform comprises adisplay generator for generating graphical user interfaces fordisplaying a representation of the 3D digital collectible in accordancewith the rules and a media player for playing the digital media filesincluded with the 3D digital collectible based on scripted or userselected commands. The interface may be configured to display the 3Ddigital collectible as a virtual, three dimensional n-sided structurediscussed above.

According to another aspect of the invention, based on a set of rulesand/or data, the display generator may be configured to depict arepresentation of a media file on at least one surface of the 3D digitalcollectible (e.g., when a representation of a first surface of the 3Dvirtual display element is forward facing) and the at least some of thedata or other content on another surface or surfaces of the 3D digitalcollectible when that surface of the 3D digital collectible is forwardfacing. Forward facing may refer to when a surface of the 3D virtualdisplay element is displayed as user facing when viewed from theperspective of a user, such the surface, or at least a portion thereofis viewable by a user looking at the display on which the 3D virtualdisplay element is rendered.

According to another aspect of the invention, the 3D virtual displayelement representing the 3D digital collectible may be dynamic, suchthat it is rotatable to display one or more of the surfaces and theassociated content (e.g., media file, data and/or content) assigned tothat surface.

According to another aspect of the invention, the interface may befurther configured such that when a surface of the 3D digitalcollectible depicting a representation of a media file is forwardfacing, a script or user command may cause the media player to play oneor more media files representing the event. The digital media files maycomprise a video clip of the event or multiple clips of the event fromdifferent perspectives. The multiple clips may be associated with thecollectible in a data structure stored in the memory. The multiple clipsmay be played sequentially (e.g., in accordance with a script) or theymay be stitched together in a specified order to create a single file.

According to another aspect of the invention, the event may include ahighlight from any type or category of experience, including withoutlimitation any a sporting match . In the context of a sporting match,the highlight may include a video clip of the highlight, such as aplayer dunking a basketball or any other event from any type of sportsmatch).The events are not limited to sports. The event may be video orother form of capture of any of a number of other experiences ,including without limitation, sports, athletic events, esports and othercompetitions or other participatory experiences, artistic or theatricalproductions (such as a show, play, concert, opera or other production),an awards show, a television show, movie, game, streaming media, socialmedia or other entertainment experience, an information experience suchas a speech, news report, political debate or other informationexperience other categories of events or experiences. The platformdescribed is intended to cover a wide variety of event types from a widevariety of experiences.

According to another aspect of the invention, various types of mediafiles, data and other content may be associated and stored with theevent. A first type of data may include event data that describes theevent itself. In the context of a sporting match, the event data mayinclude the player, the type of action (e.g., a dunk, block, steal orother action), the date of the event, and other event data. A secondtype of data may include actor data relating to the person captured inthe event. For example, in the context of a sporting match, the actordata may include the player's age, hometown, college, statistics andother actor-related data. A third type of data may include context datathat describes additional information about the context of the event.For example, in connection with a sporting match, the context data mayinclude the teams that were playing when the event was captured, wherethe game was being played, the score of the game, and other contextdata). The media file, the various associated types of data and otheritems associated with an event may be collectively referred to ascontent. In some embodiments, the content is stored in memory inassociated with the event (or an event identifier) and at least some ofthe content may be selectively displayed on the 3D visual displayelement in accordance with a set of rules and/or metadata.

According to another aspect of the invention, the data associated withan event may also include metadata. Metadata may include informationspecified in connection with the creation of the digital collectiblethat specifies the content to be displayed and the manner in which thecontent should be displayed, such as what content should be displayed,where the content should be displayed (e.g., which surface), and how thedata should be displayed. Other metadata may include informationassociated with the classification of the digital collectible or otherinformation relating to the collectible.

According to another aspect of the invention, the process of creating a3D digital collectible may include specifying the content to bedisplayed on the 3D digital collectible and the surfaces to which thedata is to be assigned.

The above stated aspects, as well as other aspects, features andadvantages of the invention will become clear to those skilled in theart upon review of the following description. It should be understoodthat the description and specific examples, while describing severalexemplary embodiments, are intended for purposes of illustration onlyand are not intended to limit the scope of the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and/or other aspects of the invention will be more apparent bydescribing in detail exemplary embodiments of the invention withreference to the accompanying drawings, in which:

FIGS. 1a-1e shows a 3D digital collectible according to some embodimentsof the invention;

FIGS. 2a-2m show aspects of a 3D digital collectible according to someembodiments of the invention;

FIGS. 3a and 3b show a digital media playing applications according tosome embodiments of the invention;

FIG. 4 shows aspects of a 3D digital collectible management systemaccording to some embodiments of the invention;

FIG. 5 shows aspects of a 3D digital collectible creation processaccording to some embodiments of the invention; and

FIGS. 6a-6d show aspects of user controllable viewing tools according tosome embodiments of the invention.

DETAILED DESCRIPTION OF THE INVENTION

Exemplary embodiments of the invention will now be described below byreference to the attached Figures. The described exemplary embodimentsare intended to assist the understanding of the invention and are notintended to limit the scope of the invention in any way. Like referencenumerals refer to like elements throughout. The examples are provided inconnection with a sports event by way of example only. The platform maybe used with other events including the other types of events referencedherein and other types of events.

The 3D Digital Collectible

Aspects of various types of events may include important portions whichcan be captured (as digital media files or other forms of capture). Suchdigital media files may include videos, images, sounds, and or otherforms of capture that record a particular event during an experience.For example, in relation to sports, an event can be a particular play,such as a dunk in a basketball game, a goal in a soccer match, or acatch in baseball. In such examples, the event may be captured as avideo, audio and/or other form of highlight, including from one or moreperspective views, as a digital media file or files. The event can be ofdifferent durations appropriate to memorialize the event. An event maybe part of a live-action experience, such as a sporting match or play,or a scripted or pre-recorded experience, such as a movie.

In an exemplary embodiment, a 3D digital collectible may be defined,generated, and rendered. The 3D digital collectible may include adigital media file (e.g., a video highlight clip) or a set of digitalmedia files (e.g., different perspectives of the same event or a seriesof files before, during and/or after the event) representing an event,along with data relating to the event. An event may include all or anyidentifiable portion of an experience.

The 3D digital collectible may be a virtual, three dimensional n-sidedstructure (where n is preferably greater than 3), where the n-surfacesmay be configured to form an n-sided 3D shape, such as a cube, pyramid,octagon, or other 3D shape. One or more of the surfaces may display oneor more digital media files, or portions of such digital media files,and/or one or more portions of data (or other content) in a definedrelationship stored in memory such that a particular side may display adigital media file or files, or portions thereof, a portion or portionsof data, other content or combinations thereof.

In the exemplary embodiment shown in FIG. 1 a, a 3D digital collectible100 is cube-shaped with six surfaces. In the perspective view of FIG. 1a, first surface 110 and second surface 120 are visible. First surface110 has a digital media file 115, in this case a video clip. Secondsurface 120 has data 125, in this case the logo of the team of which aplayer in digital media file 115 is a member. FIGS. 1B-le show furtherviews of 3D digital collectible 100. In FIG. 1B, another surface of 3Ddigital collectible 100 is shown. Thus surface includes data, in thiscase a team logo and score related to the event to which the 3Dcollectible is related. In FIG. 1 c, another surface of 3D digitalcollectible 100 is shown. This surface also includes data, in this casea team logo and a date and description of the event to which the 3Ddigital collectible is related. In FIG. 1 d, another perspective view of3D digital collectible 100 is shown. In this view, a surface 165 withdifferent representation of a team logo is provided, such that itappears within collectible 100, along with a surface 175 with a numberof the player shown in the video clip on surface 110. In thisembodiment, the rear of surface 110 showing digital media file 115 maybe seen through 3D digital collectible 100. In FIG. 1 e, another surfaceof 3D digital collectible 100 with a team logo and copyright and systeminformation is shown.

In various embodiments, the 3D digital collectible may be staticallydisplayed in its virtual environment(e.g. on a computer display screen),or may be dynamically displayed, such that it is rotatable to displayone or more of the surfaces and the associated content (e.g., a digitalmedia file and/or data) assigned to that surface. Such dynamic displaymay be way of interactions with a user, in response to a predefinedmovement or movements (e.g., via a script or other computer code), orcombinations thereof.

The digital media file may be any type of media, including still images,video, audio, and/or other media, or combinations of such media. Digitalmedia files may include a single view, audio track, or other recording,or composites of multiple views, audio tracks, or other recordings, suchas a composite video showing different perspectives of the event, suchas different camera views of a sports play or other event. The digitalmedia files may also include multiple views, audio tracks, or otherrecordings of the event from different perspectives, times, or durationsthat may be played sequentially and/or in other order. Such sequentialplay can be implemented by user interactions with a list of the multipleviews, audio tracks, or other recordings, by accessing the multipleviews, audio tracks, or other recordings in accordance with a script, orby stitching together the multiple views, audio tracks, or otherrecordings into a single digital media file. In this regard thecomposite or sequential digital media files may include different typesof files (e.g., they may include one or more of a video file, audiofile, or other recording). Portions of a single digital media file mayalso be identified, separated, and used as individual digital mediafiles in the manner described herein (e.g., a digital media file may besequentially divided with different portions considered as differentdigital media files). For example, a single digital media file may besequentially divided and provided on different surfaces of the 3Ddigital collectible.

The data relating to the event may include event data that describes theevent itself. Using a sporting match as an example, event data mayinclude such information as the player's name, the type of play (such asa dunk, block, or steal), the date and/or time of the event, and otherevent data. A second type of data may include actor data relating to theperson captured in the event. Again using a sporting match as anexample, actor data may include such information as the player'sstatistics, measurements, position, age, experience, hometown, college,draft selection, or other actor (or actors) data. A third type of datamay include context data that describes additional information about thecontext of the event. Again using a sporting match as an example,context data may include the teams that are playing, the location of thegame, the score of the game, the sports league, the sports season, andcontext data. The digital media file and any related data and/or othercontent may be collectively referred to as content.

Further exemplary embodiments of context data include informationrelated to an entertainment experience from which the event is drawn,situational information related to the entertainment experience, thesubject of the experience, and/or information related to the digitalmedia file. For example, context data related to a sporting match mayinclude the number of teams, the box score, game statistics, seasonalaverages for the player, media about the game, and other context data.In the sporting match example, the context data may relate to one ormore players or teams that are represented in a digital media file.

The various forms of data may be associated with a digital media file inany known manner, such as by tags, attributes, metadata, pointers and/orother associations. Data may be stored in a data structure in one ormore databases. The data structures may link an event with media files,data, content and metadata. The event and/or digital media file can besearched based on information associated with the event or the digitalmedia file.

Data may also include metadata. Metadata may include informationspecified in connection with the creation of the 3D digital collectiblethat specifies attributes of the digital collectible. The attributes mayinclude the configuration of the digital collectible (e.g. the number ofsides) the manner in which content should be displayed, such as whatcontent should be displayed, where the content should be displayed(e.g., on which surface of the n-shape), and how the content should bedisplayed, including in relation to other content. Other attributes ofthe digital collectible may be used.

Metadata may also include information associated with the uniqueness orclassification of the scarcity of the digital collectible. For example,a collectible may be a one of a kind instance of an event or there maybe a predetermined number of instances or other methods for determininga number of instances. In any case, the digital collectible may beidentified by a serial number or other unique value that uniquelyidentifies a particular 3D digital collectible, along with a uniqueidentifier for the instance (e.g., 1 of 1 or 1 of 10, etc.) asnecessary.

Scarcity may be represented by a classification based on the number ofinstances. For example, more than 1000 instances may be a firstclassification, 500-1000 may be another classification, 100-500 may beanother classification, and so on. Other numbers may be used tocategorize scarcity classifications. The uniqueness or scarcity (e.g.,the number of instances) can be set for an individual 3D digitalcollectible as part of the initial creation process in defining thecollectible. The metadata may include data that dictates how the 3Ddigital collectible is rendered for display based on the scarcity of the3D digital collectible. For example, data relating to the uniqueness orscarcity of the 3D digital collectible can be displayed on thecollectible, or other displayed features of the 3D digital collectiblemay relate to rarity or scarcity, such as the colors, shading, material,textures, lighting and/or visual display indicators that depict ascarcity classification.

The digital media file and data may also be created based on anotherdigital media file or data. For example, a digital media file includinga graphic and/or sound may be generated based on a digital media fileincluding a video. As such, 3D digital collectibles can include one ormore related digital media files and data.

System

A platform 400 for creating, managing, storing, rendering, anddisplaying 3D digital collectibles according to an exemplary embodimentof the invention is shown in FIG. 4. FIG. 4 shows system 410 withvarious modules and engines for defining, generating, and rendering a 3Ddigital collectible, system storage 430 for storing data, digital mediafiles, 3D collectibles, and collection information, and display 470 fordisplaying the 3D digital collectible to a user.

System 410 may include a computer server including a processor 412programmed with computer instructions including an administration module414, a display generator 416, a rendering engine 418, a gathering engine420, a collectible creation manager 422, a user account manager 424, auser control module 426, and a collection manager 428. Platform 400 mayalso include a display 470 with 3D display 472 and media player 474.Platform 400 may also include an associated computer memory or systemstorage 430 that stores a data structure comprising event data 432,actor data 434, context data 436, metadata 438, digital media files 440.3D collectibles 442, scarcity data 444, and collection data 446,associated data/content, and particular association(s) therebetween,including rules that define what is to be displayed on the surfaces ofthe 3D digital collectible. The components of the systems may beco-located or distributed.

Platform 400 may include tools to define and create a 3D digitalcollectible, including administration module 414 that manages and tracksownership of 3D digital collectibles by particular users, gatheringengine that collects digital media files and data from event 450 and/orother data sources, and collectible creation manager 422 that creates 3Ddigital collectibles and defines their data structures andrelationships. User account manager 424 is also provided to allow usersto create and manage accounts to interact with system 410, and usercontrol module 426 that provides various controls to users to performany of the steps herein.

As part of the process for creating a 3D digital collectible, gatheringengine 420 may gather digital media files 452 and data 454 related to anevent, either automatically or pursuant to a specific user request. Thisgathering may include obtaining necessary rights to the digital mediafiles 452 or data 454. Gathering engine 420 may then store collecteddigital media files 452 in system storage 430 as stored digital mediafiles 440. Gathering engine 420 may also store data 454 in systemstorage 430 as event data 432, actor data 434, or context data 436, asappropriate. Gathering engine 420 may also gather and store event data432, actor data 434, and context data 436 from other sources related toevent 450, such as other databases or data services related to news,statistics, sports leagues, etc.

Collectible creation manager 422 may use the stored digital media files440 and data 432, 434, 436, and 438 to create a 3D digital collectibleand store it in system storage 430 as a stored 3D digital collectible443. Each stored 3D digital collectible 440 may include a globallyunique identifier. Collectible creation manager 422 providesfunctionality to specify the type of 3D digital collectible (e.g., whatn-sided 3D shape is to be used), visual design attributes of the 3Ddigital collectible (e.g., colors, shading, material, textures, and/orlighting), which digital media file(s) 440 and data 432, 434, 436, and438 are to be displayed on the 3D digital collectible, how the digitalmedia file(s) and data are to be displayed (e.g., what surfaces thecontent is to be assigned, how the content is to be shown, played, orlistened to, any sequence of display, etc.), a scarcity classificationof the 3D digital collectible, obtained from scarcity data 444, and anyother of the related elements discussed herein. Collectible creationmanager 422 may provide a GUI for a user to create a 3D digitalcollectible and select each of the above parameters, or may operate in apartially or fully automatic manner. After each of the parameters aboveare selected, collectible creation manager 422 may establishassociations or links between the 3D digital collectible (such as byusing its unique identifier) and any applicable digital media file(s)440, data 432, 434, 436, or 438, and any other applicable data or designelements, and creates a data structure in memory associating theseelements. This data structure is associated with the 3D digitalcollectible being created and is stored as metadata 438 in systemstorage 430. In this manner, each 3D digital collectible created bycollectible creation manager 422 is unique based on the aspects of theembodiments described herein.

Collectible creation manager 422 may also track and store in metadata438 all relationships between event data 432, actor data 434, contextdata 436, and digital media files 440 that have been identified withregard to any other 3D digital collectible or are determined tootherwise be related during collection (e.g., event data such as a playmay be linked to context data such as the related sports league) suchthat smart options may be presented by collectible creation manager 422to a user during creation of the 3D digital collectible.

An exemplary 3D digital collectible creation process is illustrated inFIG. 5. The creator (e.g., an user with an account on system 410 astracked by user account manager 424) may employ any user interface(e.g., a GUI provided by collectible creation manager 424) or otherinput mechanisms to make the following selections and perform thefollowing data entry. In the first step 510, a user may indicate hisdesire to create a new 3D digital collectible in connection with anevent, either from preexisting media or as part of a live event. Aunique identifier for the 3D digital collectible may be selected orgenerated at this stage. In Step 520, one or more digital media filesrelated to the event (e.g., digital media files 440) may be selected andobtained, including obtaining any necessary rights to show, play, ordisplay the digital media file. In step 530, data, such as event data432, actor data 434, or context data 436 (e.g., or other data orcontent) may be identified, obtained, or entered and stored in a datastructure associated with the 3D digital collectible (e.g. as metadata438). At step 540, the creator may select visual characteristics of thedigital collectible, such as a cube or other n-sided 3D shape, and storethem in the data structure associated with the 3D digital collectible(e.g. as metadata 438). In step 550, the creator may select how thedigital media files and/or data are displayed, including how the digitalmedia files and data are displayed in relationship to each other and thevarious formats and features of the digital collectible discussedherein, and store them in the data structure associated with the 3Ddigital collectible (e.g. as metadata 438). Additionally, with regard todigital media files that include video clips, the creator may identify apicture that can be displayed on the surface of the 3D digitalcollectible as a representation of the digital media file. In variousembodiments, the picture may be a frame of the video clip or any otherpicture the creator may select. The creator may also specify thatdifferent pictures appear with regard to the digital media file indifferent situations, such as when the 3D digital collectible is indifferent orientations or after the digital media file has been playedonce.

According to another aspect of the invention, rules can be created toset forth what digital media files and data is presented on the 3Ddigital collectible as part of the 3D digital collectible creationprocess, such as in steps 520, 530, and 540 in FIG. 5. For example, the3D digital collectible may be designed to present a media file on onesurface of the 3D digital collectible (e.g., when a representation of afirst surface of the 3D virtual display element is forward facing) andrelated data on another surface or surfaces of the 3D digitalcollectible when that surface of the 3D digital collectible is forwardfacing. As a concrete example of this functionality, for a sportingevent, a highlight video can be rendered on a first surface and a teamlogo can be rendered on an opposite surface.

Rules may be stored in metadata 438, and may be accessed by collectiblecreation manager 422 during creation of the 3D digital collectible topartially automate creation, such as by automatically populating data432, 434, or 436 based on selection of a particular digital media file440, using predefined relationships between these elements as discussedabove. Rules may also enforce standardization of the appearance of 3Ddigital collectibles. For example, rules may define relationshipsbetween and among particular digital media files and data, and betweenparticular surfaces of a 3D digital collectible, such that surfaces of a3D digital collectible may be automatically populated with digital mediafiles and data in any appropriate manner. Digital media files and datamay also be classified or categorized by rules. In this manner, specificdata (i.e. belonging to a specific classification) and/or digital mediafiles may be rendered at specific surfaces of the n-surfaces of the 3Dvirtual element and can depend on data values.

Platform 400 may also include tools to display 3D digital collectibles,such as display generator 416 and rendering engine 418 for generatinggraphical user interfaces (GUIs) for displaying a 3D digital collectiblefor display therein to a user via 3D display 472 on display 470. Forexample, the 3D digital collectible (e.g. the digital media file anddata) may be configured to be displayed as a 3D display element. Thedigital collectible can be represented as, or otherwise include, the 3Ddisplay element. The 3D display element can be in a virtual 3D graphicalinterface. The 3D display element can have n-surfaces which are combinedtogether into an n-sided shape, (cube, sphere, pyramid, octagon, etc.).Each face or side of the of the n-sided shape can display at least oneof the aforementioned digital media and/or data types. Each face or sideof the n-sided shape can have associated digital media and/or contextdata of a specific type (for example, belonging to a specificclassification of media, such as images, video, text, sound forplayback, etc.).

The display generator 416 and rendering engine 618 may generate a GUI ondisplay 470, the representation of the 3D digital collectible and amedia player for playing the digital media file(s) included with the 3Ddigital collectible based on scripted or user selected commands. Theinterface may be configured to display the 3D digital collectible as thevirtual, three dimensional n-sided structure discussed above. Thedisplay may be pre-rendered or rendered in real-time as it is beingdisplayed. The 3D digital collectible may be rendered and displayed inany orientation, such as the perspective and plan views of FIGS. 1a -1e, may be stationary in one view, or may change orientation betweenviews (e.g., rotate, translate, etc.) either automatically based onelapsed time, in reaction to a user interaction (e.g., mouse click,scroll bar movement, or touch interface), or both.

When a surface of 3D digital collectible that includes a digital mediafile is facing a user, the digital media may be displayed on thatsurface (or on an overlay, as discussed below). For example, in FIG. 1a, a digital media file is visible. If the digital media file is a videoand/or audio track, display of the surface containing that digital mediafile also allows the video or audio to play. For example, in FIG. 1 a,if the displayed digital media file is a video, it may play in theorientation shown.

In other embodiments, a separate media player may be generated in theGUI by display generator 416 and rendering engine 618 to play digitalmedia files and/or data from surfaces of the 3D digital collectible,such as in an window or pop-up adjacent to the 3D digital collectible.The media player may also partially or fully overlay the 3D digitalcollectible, hover over a surface of the 3D digital collectible, orsimply replace the 3D digital collectible in the GUI. The media playermay automatically launch and begin playing when a surface of the 3Ddigital collectible with an appropriate digital media file is visible,or upon user command. The media player may be of any shape andorientation to play the media file. Additionally, the view of the mediaplayer can be changed by further user interaction. For example, themedia player may be maximized on the user screen for easier viewingautomatically or based on user command. Selectors may also be providedto perform other display changes, or to launch a separate viewer orapplication.

FIGS. 3A and 3B illustrate exemplary embodiments of media player 474.FIG. 3A provides the media player over the surface of the 3D digitalcollectible, while FIG. 3B shows the media player partially overlayingthe 3D digital collectible. In either of these embodiments, the 3Ddigital collectible and media player may be provided in the same window,or in separate windows or popups. In any of the embodiments discussedabove, the media player may be partially transparent such that portionsof the 3D digital collectible under the media player are still visible.In any of the embodiments herein, various playback features may also beimplemented to allow the user more control of the playback, such asplay, pause, rewind, and replay buttons. Such controls may be placed onthe surface where the digital media file is shown, on the media player,or may be arranged thereto or anywhere else in the GUI.

In the above embodiments, the GUI and/or the media player may beconfigured to play the digital media file upon a direct user request, orautomatically (e.g., according to timing or positioning of the 3Ddigital collectible). For example, the GUI may be configured such thatwhen a surface of the 3D digital collectible depicting a representationof a media file is forward facing, a script or user command may causethe media player to play one or more media files representing the event.As discussed above, the digital media files may comprise a video clip ofthe event or multiple clips of the event from different perspectives.The multiple clips may be associated with the collectible in a datastructure stored in the memory. The multiple clips may be playedsequentially (e.g., in accordance with a script) or they may be stitchedtogether in a specified order to create a single file.

According to another exemplary embodiment, the GUI may be an interactivedisplay. For example, in response to user input selections via thegraphical user interface different surfaces of the n-sided display maybe displayed. For example, as shown in FIGS. 6a -6 d, GUI 650 may beconfigured to include a first display portion 600 with a set of icons602, 604, 606, 608, 610, 612 and second display portion 620 that showsvarious views of a 3D digital collectible corresponding to the icons. Asshown in FIG. 6d , media player 660 may also be launched in seconddisplay portion 620. Features of an interactive display are described inmore detail in a U.S. Application filed Apr. 13, 2021 as Attorney DocketNo. 77HN-332438, hereby incorporated by reference in its entirety.

Modifying the Shape of 3D Digital Collectibles

In still another example, the GUI may be configured to allow the user tomanipulate the shape of the 3D digital collectible, and the displayedmedia can change to accommodate the shape. The data may also changeand/or be updated depending on the user manipulation. In embodiments,manipulation of the shape can “unlock” display of specific digital mediaand/or data, and/or adjust data.

In yet another embodiment, the shape of the 3D digital collectible maychange based on continued user interaction. For example, the shape ofthe 3D digital collectible may change based on the number of times it isaccessed, displayed, traded, or other interactions or predeterminedfactors, or if the 3D digital collectible reaches a certain value.Alternatively, the shape of the 3D digital collectible may change if twoor more 3D digital collectibles are combined to create new 3D digitalcollectible.

Managing a Collection of 3D Digital Collectibles

According to other aspects of various embodiments, a user may manage thedisplay of multiple digital collectables within their account throughcollection manager 428. For example, in some embodiments, the digitalcollectables may be stored online (e.g., under control of the system), auser may create one or more collections of digital collectables andshare a link or other identifier associated with the collection andother users may use the link or other identifier to view thecollection(s). Data related to the collection may be stored ascollection data 446. Collections are described in more detail in a U.S.Application filed Apr. 13, 2021 as Attorney Docket No. 77HN-332438,hereby incorporated by reference in its entirety.

Example 3D Digital Collectibles

FIGS. 2a-2m show further exemplary embodiments of 3D digitalcollectibles that include one or more of the features discussed above,along with various additional features.

In FIG. 2a , exemplary 3D digital collectible 200 a includes a 3Ddisplay element in the shape of a cube having vertices 201-A through201-H defining 6 surfaces 203 a (the n-surfaces of the example). This 3Ddisplay element may be a virtual 3D graphical interface. At least onedigital media file and/or data (such as the event data, actor data, orcontext data described above) may be rendered on one or more of thesurfaces. Although 3D digital collectible 200 a is shown with 8 verticesand six surfaces, it is understood that 3D digital collectible 200 a mayhave any number of vertices, surfaces, indentations, depressions,protrusions, etc.

In FIG. 2b , exemplary 3D digital collectible 200 b includes a firstdigital media file 205 b (e.g. a video, image, and/or sound), and asecond digital media file 207 b (e.g. video, image, and/or sound) onparticular surfaces (e.g. opposite or adjacent surfaces). In thisembodiment, the digital media files 205 b and 207 b are associated witha live entertainment event. For example, first digital media file 205 bincludes a graphical representation of a play from a basketball game(such as a dunk or other score), and second digital media file 207 bincludes digital media related to the play represented in the firstdigital media file 205 b (such as a video highlight of the play). Asdescribed above, the first and second digital media files may also becomposites or two different sequential portions of an original digitalmedia file that have been divided.

In exemplary embodiments, particular faces or sides of an n-sided 3Ddigital collectible may include at least one digital media file (such asthose exemplified above) or at least a portion of data (such as theevent data, actor data, or context data described above). Each of thefaces or sides of an n-sided 3D digital collectible may include suchdigital media files or data, or a subset of the surfaces may includeother information or data, or no information or data. The n-sided shapemay have one or more edges and/or surfaces that can be defined by one ormore colors, shading, lighting, and/or textures. The colors, shading,material, textures, and/or lighting can correspond to data values. Itcan also be understood that display of digital media and/or values fordata can be presented in spatial and/or temporal arrangements, and/or atone or more faces of the n-sided shape. Each face or side of the n-sidedshape can have associated digital media and/or metadata of a specifictype. Each side may have one or more types of content and any piece ofcontent may span multiple sides. Reference to content on a surface mayinclude display of content on a portion of the surface.

In another exemplary embodiment, a 3D digital collectible may alsoinclude a substantially transparent overlay portion over at least onesurface of the n-sided 3D shape. The overlay may display additionaldigital media files or data in relation to digital media files or datadisplayed on a surface of the n-sided shape. For example, a 3D digitalcollectible may display a digital media file of an event (e.g., a videoof a dunk) on a visible one of its n surfaces and its overlay portionmay display data related to the event (e.g., displaying the player'sname overlaying the video of the dunk). The content to be displayed onthe overlay portion, and the manner it is displayed, can be specifiedduring the creation process in the manner discussed above.

In FIG. 2c , an exemplary overlay related to 3D digital collectible 200c is shown. In this embodiment, the overlay is defined by one or moreedges, or markers 210 c that may be of a different transparency than theoverlay. As is shown in FIG. 2c , an overlay can include surfacesdefined by markers, for example at the corners of a side. Here, theoverlay is defined by eight markers 210, such that each surface isdefined by four markers 210 c.

In FIG. 2d , the surfaces of the overlay are arranged in a cube shapeabout 3D digital collectible 200 d with surfaces 203 d including a firstdigital media file 205 d (e.g. video, image, and/or sound), and a seconddigital media file 207 d (e.g. video, image, and/or sound) displayedthereon. The overlay surfaces are defined by markers 210 d. In exemplaryembodiments, the overlay area can render or otherwise include portionsof data (such as the event data, actor data, or context data describedabove) and/or additional digital media files.

The overlay can be 2-dimensional in front of a n-sided 3D displayelement, or a 3D shape that “surrounds” the n-sided 3D display element.The 3D shape of the overlay may be the same as the n-sided 3D displayelement or different. The overlay area may be movable, such as by theuser sliding, translating, or rotating it, compared to the 3D displayelement, or in conjunction with the 3D display element.

The exemplary embodiment of FIG. 2e demonstrates different perspectivesof a user viewing 3D digital collectible 200 e, including a firstperspective 220 viewing a first side, a second perspective 221 viewing asecond side, a third perspective 222 viewing a third side, and a fourthperspective 223 viewing a fourth side. As shown by the variousperspectives, a display of a representation of a digital media file orvarious portions of data depend on which surface of the 3D displayelement is forward facing.

For example, the digital media collectible 200 e of FIG. 2e includes a3D display element and transparent overlay (defined by markers 210 e) aspreviously discussed. As shown in the first perspective 220 viewing thefirst side of the digital collectible 200 e, a first digital media file225 e can be rendered for display at a surface of the digitalcollectible. Further, data, such as the event data, actor data, orcontext data, can be rendered for display at the overlay.

When the digital collectible 200 e (e.g. the 3D shape and/or the overlayarea) is manipulated by the user, the information or data shown in theoverlay area with respect to the first side, may not be depictedassociated to the same side anymore, and/or can be associated to a sideother than the data shown at the first side. In other words, aftermanipulation by the user, digital media 225 e and data 226 e can bedepicted as belonging to other sides.

As shown in the second perspective 221 viewing the second side, one ormore portions of data may be displayed) like the type of play 227 e(e.g. dunk corresponding to a basketball play or move), the score 228 orother statistic, the team names 229, and other information 230 e (suchas the date or time for the entertainment experience, etc.). The secondside of the digital collectible can also display other graphical data ordigital media files.

As shown in the third perspective 222 viewing the third side, anotherportion of data may be displayed, such as additional context informationlike the player number 231 e, in conjunction with another digital mediafile, such as an image of the player 232 e, as well as other contextinformation such as the player name 233 e.

As shown in the fourth perspective 223 viewing the fourth side of thedigital media collectible 200 e, other portions of data or digital mediafiles may be displayed, such as a logo for the team 234 e.

FIGS. 2f-2i show various embodiments of overlays. FIG. 2f showsexemplary 3D digital collectible 200 f with a 2D transparent overlay 240f which overlays one side of the n-shape of 3D digital collectible 200 fAs shown in FIG. 2f , overlay 240 f need not be defined by anon-transparent marker or edge. FIG. 2g shows exemplary 3D digitalcollectible 200 g with 2D transparent overlay 240 g which overlays oneside of the n-shape of 3D digital collectible 200 g, like the embodimentof FIG. 2f . In this embodiment, 2D transparent area 240 g includes oneor more edges or markers 210 g. FIG. 2h shows exemplary 3D digitalcollectible 200 h that is similar to the embodiment of FIG. 2g , butprovides a 2D transparent overlay 240 h including one or more markers210 h. Finally, FIG. 2i shows exemplary 3D digital collectible 200 ithat is similar to the embodiment of FIG. 2g , but which provides a 3Doverlay 240 i including one or more edges or markers 210 i. In variousembodiments, the type of overlay (e.g. attributes thereof, such aswhether 2D or 3D, the surface of the n-shape that it overlays, the typeand/or number of markers, etc.) can depend on the data associated withthe 3D digital collectible, the event data, actor data, context data,and/or metadata. For example, the overlay type may depend on andcorrespond to the rarity or scarcity of the digital collectible.

FIGS. 2j, 2k , 21, 2 m, depict exemplary embodiments of digitalcollectibles with various types of markers. FIG. 2j shows digitalcollectible 200 j with media 205 j and an overlay area including one ormore bar-shaped edges or markers 210 j. FIG. 2 jk shows digitalcollectible 200 k with media 205 k and an overlay including one or morecorner-shaped edges or markers 210 k to frame the corners of theoverlay. FIG. 210l shows digital collectible 200 l with media 205 l andoverlay area including one or more corner-shaped edges or markers 210 lthat define one or more corners of the overlay area. Finally, FIG. 210mshows digital collectible 200 m with media 205 m and overlay areaincluding one or more triangular-shaped edges or markers. Variousadditional shapes for markers may be used, as well as variouscombinations thereof.

Processing Devices and Processors

In some embodiments, the platforms, systems, media, and methodsdescribed herein, including system 400, include a processing devices,processors, or use of the same. In further embodiments, the processingdevice includes one or more hardware central processing units (CPUs) orgeneral purpose graphics processing units (GPUs) that carry out thedevice's functions. In still further embodiments, the processing devicefurther comprises an operating system configured to perform executableinstructions. In some embodiments, the processing device is optionallyconnected a computer network. In further embodiments, the processingdevice is optionally connected to the Internet such that it accesses theWorld Wide Web. In still further embodiments, the processing device isoptionally connected to a cloud computing infrastructure. In otherembodiments, the processing device is optionally connected to anintranet. In other embodiments, the processing device is optionallyconnected to a data storage device. In accordance with the descriptionherein, suitable processing devices include, by way of non-limitingexamples, cloud computing resources, server computers, server clusters,desktop computers, laptop computers, notebook computers, sub-notebookcomputers, netbook computers, netpad computers, handheld computers,mobile smartphones, and tablet computers. In some embodiments, theprocessing device includes an operating system configured to performexecutable instructions. The operating system is, for example, software,including programs and data, which manages the device's hardware andprovides services for execution of applications. Those of skill in theart will recognize that suitable server operating systems include, byway of nonlimiting examples, FreeBSD, OpenBSD, NetBSD®, Linux, Apple®Mac OS X Server®, Oracle® Solaris®, Windows Server®, and Novell®NetWare®. Those of skill in the art will recognize that suitablepersonal computer operating systems include, by way of non-limitingexamples, Microsoft ® Windows®, Apple® Mac OS X®, UNIX®, and UNIX-likeoperating systems such as GNU/Linux®. In some embodiments, the operatingsystem is provided by cloud computing. Those of skill in the art willalso recognize that suitable mobile smartphone operating systemsinclude, by way of non-limiting examples, Nokia® Symbian® OS, Apple®iOS®, Research In Motion® BlackBerry OS®, Google® Android®, MicrosoftWindows Phone® OS, Microsoft Windows Mobile® OS, Linux®, and Palm®WebOS®. In some embodiments, the processing device includes a storageand/or memory device. The storage and/or memory device is one or morephysical apparatuses used to store data or programs on a temporary orpermanent basis. In some embodiments, the device is volatile memory andrequires power to maintain stored information. In some embodiments, thedevice is non-volatile memory and retains stored information when theprocessing device is not powered. In further embodiments, thenon-volatile memory comprises flash memory. In some embodiments, thenonvolatile memory comprises dynamic random-access memory (DRAM). Insome embodiments, the non-volatile memory comprises ferroelectric randomaccess memory (FRAM). In some embodiments, the non-volatile memorycomprises phase-change random access memory (PRAM). In otherembodiments, the device is a storage device including, by way ofnon-limiting examples, CD-ROMs, DVDs, flash memory devices, magneticdisk drives, magnetic tapes drives, optical disk drives, and cloudcomputing based storage. In further embodiments, the storage and/ormemory device is a combination of devices such as those disclosedherein. In some embodiments, the processing device includes a display tosend visual information to a user. In some embodiments, the display is acathode ray tube (CRT). In some embodiments, the display is a liquidcrystal display (LCD). In further embodiments, the display is a thinfilm transistor liquid crystal display (TFT-LCD). In some embodiments,the display is an organic light emitting diode (OLED) display. Invarious further embodiments, on OLED display is a passive-matrix OLED(PMOLED) or active matrix OLED (AMOLED) display. In some embodiments,the processing device includes an input device to receive informationfrom a user. In some embodiments, the input device is a keyboard. Insome embodiments, the input device is a pointing device including, byway of non-limiting examples, a mouse, trackball, track pad, joystick,game controller, or stylus. In some embodiments, the input device is atouch screen or a multi-touch screen. In other embodiments, the inputdevice is a microphone to capture voice or other sound input. In otherembodiments, the input device is a video camera or other sensor tocapture motion or visual input. In still further embodiments, the inputdevice is a combination of devices such as those disclosed herein.

Referring to FIG. 4, in an exemplary platform 400, an exemplary system410 is programmed or otherwise configured to, for example, dynamicallyload data provider connector modules and/or request, procure, process,analyze, persist and/or provide one or more data records. In thisembodiment, the system 400 includes a processor 412 (also known as acentral processing unit (CPU) and “computer processor”), which can be asingle core or multi core processor, or a plurality of processors forparallel processing. System 410 also includes memory or memory location(e.g., random-access memory, read-only memory, flash memory), systemstorage 430 (e.g., hard disk), a communication interface (e.g., networkadapter) for communicating with one or more other systems, andperipheral devices, such as cache, other memory, data storage and/orelectronic display adapters. The memory, system storage 430, networkinterface and peripheral devices are in communication with the CPU 412through a communication bus, such as a motherboard. The system storage430 can be a data storage unit (or data repository) for storing data.System 410 can be operatively coupled to a computer network (“network”)with the aid of the communication interface. The network can be theInternet, an internet and/or extranet, or an intranet and/or extranetthat is in communication with the Internet. The network in some cases isa telecommunication and/or data network. The network can include one ormore computer servers, server clusters and/or distributed computingresources, providing, for example cloud computing. The network, in somecases with the aid of the system 410, can implement a peer-to-peernetwork, which may enable devices coupled to the device 501 to behave asa client or a server.

In some embodiments, the CPU 412 can execute a sequence ofmachine-readable instructions, which can be embodied in a program orsoftware. The instructions may be stored in a memory location, such asthe memory. The instructions can be directed to the CPU 412, which cansubsequently program or otherwise configure the CPU 412 to implementmethods of the present disclosure. The CPU 412 can be part of a circuit,such as an integrated circuit. One or more other components of thesystem 410 can be included in the circuit. In some cases, the circuit isan application specific integrated circuit (ASIC) or a fieldprogrammable gate array (FPGA).

In some embodiments, the system storage 430 can store files such asdrivers, libraries and saved programs. The system storage 430 can storeuser data, e.g., user preferences and user programs. The system 410 insome cases can include one or more additional data storage units thatare external, such as located on a remote server, remote server cluster,network attached storage, or the like, that is in communication throughan intranet or the Internet. In some embodiments, methods as describedherein can be implemented by way of machine (e.g., computer processor)executable code stored on an electronic storage location of the system410, such as, for example, on the memory or system storage 430. Themachine executable or machine readable code can be provided in the formof software. During use, the code can be executed by the CPU 412. Insome cases, the code can be retrieved from the system storage 430 andstored on the memory for ready access by the CPU 412. In somesituations, the system storage 430 can be precluded, andmachine-executable instructions are stored on memory. In someembodiments, the code is pre-compiled. In some embodiments, the code iscompiled during runtime. The code can be supplied in a programminglanguage that can be selected to enable the code to execute in aprecompiled or as-compiled fashion.

In some embodiments, the system 410 can include or be in communicationwith an electronic display 470. In some embodiments, the electronicdisplay 470 provides a user interface or GUI.

Non-Transitory Computer Readable Storage Medium

In some embodiments, the platforms, systems, media, and methodsdisclosed herein include one or more non-transitory computer readablestorage media encoded with a program including instructions executableby the operating system of an optionally networked processing device. Infurther embodiments, a computer readable storage medium is a tangiblecomponent of a processing device. In still further embodiments, acomputer readable storage medium is optionally removable from aprocessing device. In some embodiments, a computer readable storagemedium includes, by way of non-limiting examples, CD-ROMs, DVDs, flashmemory devices, solid state memory, magnetic disk drives, magnetic tapedrives, optical disk drives, distributed computing systems includingcloud computing systems and services, and the like. In some cases, theprogram and instructions are permanently, substantially permanently,semi-permanently, or non-transitorily encoded on the media.

Computer Program

In some embodiments, the platforms, systems, media, and methodsdisclosed herein include at least one computer program, or use of thesame. A computer program includes a sequence of instructions, executablein the processing device's CPU, written to perform one or more specifiedtasks. Computer readable instructions may be implemented as programmodules, such as functions, objects, Application Programming Interfaces(APIs), data structures, and the like, that perform particular tasks orimplement particular abstract data types. In light of the disclosureprovided herein, those of skill in the art will recognize that acomputer program may be written in various versions of variouslanguages. The functionality of the computer readable instructions maybe combined or distributed as desired in various environments. In someembodiments, a computer program comprises one sequence of instructions.In some embodiments, a computer program comprises a plurality ofsequences of instructions. In some embodiments, a computer program isprovided from one location. In other embodiments, a computer program isprovided from a plurality of locations. In various embodiments, acomputer program includes one or more software modules. In variousembodiments, a computer program includes, in part or in whole, one ormore web applications, one or more mobile applications, one or morestandalone applications, one or more web browser plug-ins, extensions,add-ins, or add-ons, or combinations thereof.

Web Application

In some embodiments, a computer program includes a web application. Inlight of the disclosure provided herein, those of skill in the art willrecognize that a web application, in various embodiments, utilizes oneor more software frameworks and one or more database systems. In someembodiments, a web application is created upon a software framework suchas Microsoft®.NET or Ruby on Rails (RoR). In some embodiments, a webapplication utilizes one or more database systems including, by way ofnon-limiting examples, relational, non-relational, object oriented,associative, and XML database systems. In further embodiments, suitablerelational database systems include, by way of non-limiting examples,Microsoft® SQL Server, mySQLTM, and Oracle®. Those of skill in the artwill also recognize that a web application, in various embodiments, iswritten in one or more versions of one or more languages. A webapplication may be written in one or more markup languages, presentationdefinition languages, client side scripting languages, server-sidecoding languages, database query languages, or combinations thereof. Insome embodiments, a web application is written to some extent in amarkup language such as Hypertext Markup Language (HTML), ExtensibleHypertext Markup Language (XHTML), or eXtensible Markup Language OiML).In some embodiments, a web application is written to some extent in apresentation definition language such as Cascading Style Sheets (CSS).In some embodiments, a web application is written to some extent in aclient-side scripting language such as Asynchronous JavaScript and XML(AJAX), Flash® ActionScript, Javascript, or Silverlight®. In someembodiments, a web application is written to some extent in aserver-side coding language such as Active Server Pages(ASP),ColdFusion®, Perl, Java™, JavaServer Pages (JSP), Hypertext Preprocessor(PHP), Python™, Ruby, Tcl, Smalltalk, WebDNA®, or Groovy. In someembodiments, a web application is written to some extent in a databasequery language such as Structured Query Language (SQL). In someembodiments, a web application integrates enterprise server productssuch as IBM® Lotus Domino®. In some embodiments, a web applicationincludes a media player element. In various further embodiments, a mediaplayer element utilizes one or more of many suitable multimediatechnologies including, by way of nonlimiting examples, Adobe® Flash®,HTML 5, Apple® QuickTime®, Microsoft® Silverlight®, Java™, and Unity®.

Mobile Application

In some embodiments, a computer program includes a mobile applicationprovided to a mobile processing device. In some embodiments, the mobileapplication is provided to a mobile processing device at the time it ismanufactured. In other embodiments, the mobile application is providedto a mobile processing device via the computer network described herein.

In view of the disclosure provided herein, a mobile application iscreated by techniques known to those of skill in the art using hardware,languages, and development environments known to the art. Those of skillin the art will recognize that mobile applications are written inseveral languages. Suitable programming languages include, by way ofnon-limiting examples, C, C++, C#, Objective-C, Java™, Javascript,Pascal, Object Pascal, Python™, Ruby, VB .NET, WML, and XHTML/HTML withor without CSS, or combinations thereof.

Suitable mobile application development environments are available fromseveral sources. Commercially available development environmentsinclude, by way of non-limiting examples, AirplaySDK, alcheMo,Appcelerator®, Celsius, Bedrock, Flash Lite, .NET Compact Framework,Rhomobile, and WorkLight Mobile Platform. Other development environmentsare available without cost including, by way of non-limiting examples,Lazarus, Mobi-Flex, MoSync, and Phonegap. Also, mobile devicemanufacturers distribute software developer kits including, by way ofnon-limiting examples, iPhone and iPad (iOS) SDK, AndroidTM SDK,BlackBerry® SDK, BREW SDK, Palm® OS SDK, Symbian SDK, webOS SDK, andWindows® Mobile SDK.

Those of skill in the art will recognize that several commercial forumsare available for distribution of mobile applications including, by wayof non-limiting examples, Apple® App Store, Google® Play, Chrome WebStore, BlackBerry® App World, App Store for Palm devices, App Catalogfor webOS, Windows® Marketplace for Mobile, Ovi Store for Nokia®devices, Samsung® Apps, and Nintendo® DSi Shop.

Software Modules

In some embodiments, the platforms, systems, media, and methodsdisclosed herein include software, server, and/or database modules, oruse of the same. In view of the disclosure provided herein, softwaremodules are created by techniques known to those of skill in the artusing machines, software, and languages known to the art. The softwaremodules disclosed herein are implemented in a multitude of ways. Invarious embodiments, a software module comprises a file, a section ofcode, a programming object, a programming structure, or combinationsthereof. In further various embodiments, a software module comprises aplurality of files, a plurality of sections of code, a plurality ofprogramming objects, a plurality of programming structures, orcombinations thereof. In various embodiments, the one or more softwaremodules comprise, by way of nonlimiting examples, a web application, amobile application, and a standalone application. In some embodiments,software modules are in one computer program or application. In otherembodiments, software modules are in more than one computer program orapplication. In some embodiments, software modules are hosted on onemachine. In other embodiments, software modules are hosted on more thanone machine. In further embodiments, software modules are hosted oncloud computing platforms. In some embodiments, software modules arehosted on one or more machines in one location. In other embodiments,software modules are hosted on one or more machines in more than onelocation.

Databases

In some embodiments, the platforms, systems, media, and methodsdisclosed herein include one or more databases, or use of the same. Inview of the disclosure provided herein, those of skill in the art willrecognize that many databases are suitable for storage and retrieval ofdata, such as digital media collectibles described herein. In variousembodiments, suitable databases include, by way of non-limitingexamples, relational databases, nonrelational databases, object orienteddatabases, object databases, entity-relationship model databases,associative databases, and XML databases. In some embodiments, adatabase is web-based. In still further embodiments, a database is cloudcomputing-based. In other embodiments, a database is based on one ormore local computer storage devices.

Various methods have been described herein to generate, maintain, anddisplay 3D digital collectibles, including methods using exemplarysteps. It may be understood that more or less steps may be included, andthat the illustrated steps are merely non-limiting examples. Nor is theorder in which the steps are presented/described indicative of any setor requisite order that must be followed. It should be appreciated thatvarious prompts, cues, buttons, and/or other graphical/visualinteractive elements may be presented to the user together with one ormore of these steps. Steps depicted herein may correspond toinstructions stored in computer readable storage medium which can beexecuted by one or more processors of computing components describedherein, for example as part of computing components disclosed herein

While the invention has been particularly shown and described withreference to exemplary embodiments thereof, the invention is not limitedto these embodiments. It will be understood by those of ordinary skillin the art that various changes in form and details may be made thereinwithout departing from the spirit and scope of the invention as definedby the following claims.

What is claimed is:
 1. A method comprising: generating, by one or moreprocessors, a 3D virtual display element having a plurality of surfacesand configured to display a representation of a media file of an eventin response to a first surface of the plurality of surfaces facingforward, to display first data of the event in response to a secondsurface of the plurality of surfaces facing forward, and to displaysecond data of the event in response to a third surface of the pluralityof surfaces facing forward; causing, by the one or more processors,display of the 3D virtual display element; and activating, by the one ormore processors, a media player to play the media file of the eventoutside the first surface based on the first surface facing forward. 2.The method of claim 1, wherein the method further comprises: configuringthe 3D virtual display element to assign the representation of the mediafile of the event to the first surface of the plurality of surfaces. 3.The method of claim 1, wherein the method further comprises: configuringthe 3D virtual display element to assign the first data of the event tothe second surface of the plurality of surfaces.
 4. The method of claim1, wherein the method further comprises: configuring the 3D virtualdisplay element to assign the second data of the event to the thirdsurface of the plurality of surfaces.
 5. The method of claim 1, wherein:the first surface facing forward faces a user viewing the displayed 3Dvirtual display element.
 6. The method of claim 1, wherein the methodfurther comprises: configuring the 3D virtual display element to assignthird data of the event to a fourth surface of the plurality ofsurfaces.
 7. The method of claim 6, wherein: the event is a sports play;the media file depicts the sports play; the first data describes thesports play; the second data describes context of the sports play; andthe third data describes an actor in the sports play.
 8. Anon-transitory computer-readable storage medium comprising instructionsthat, when executed by one or more processors of a machine, cause themachine to perform operations comprising: generating a 3D virtualdisplay element having a plurality of surfaces and configured to displaya representation of a media file of an event in response to a firstsurface of the plurality of surfaces facing forward, to display firstdata of the event in response to a second surface of the plurality ofsurfaces facing forward, and to display second data of the event inresponse to a third surface of the plurality of surfaces facing forward;causing display of the 3D virtual display element; and activating amedia player to play the media file of the event outside the firstsurface based on the first surface facing forward.
 9. The non-transitorymachine-readable storage medium of claim 8, wherein the operationsfurther comprise: configuring the 3D virtual display element to assignthe representation of the media file of the event to the first surfaceof the plurality of surfaces.
 10. The non-transitory machine-readablestorage medium of claim 8, wherein the operations further comprise:configuring the 3D virtual display element to assign the first data ofthe event to the second surface of the plurality of surfaces.
 11. Thenon-transitory machine-readable storage medium of claim 8, wherein theoperations further comprise: configuring the 3D virtual display elementto assign the second data of the event to the third surface of theplurality of surfaces.
 12. The non-transitory machine-readable storagemedium of claim 8, wherein: the first surface facing forward faces auser viewing the displayed 3D virtual display element.
 13. Thenon-transitory machine-readable storage medium of claim 8, wherein theoperations further comprise: configuring the 3D virtual display elementto assign third data of the event to a fourth surface of the pluralityof surfaces.
 14. The non-transitory machine-readable storage medium ofclaim 13, wherein: the event is a sports play; the media file depictsthe sports play; the first data describes the sports play; the seconddata describes context of the sports play; and the third data describesan actor in the sports play.
 15. A system comprising: one or moreprocessors; and a memory storing instructions that, when executed by atleast one processor among the one or more processors, cause the systemto perform operations comprising: generating a 3D virtual displayelement having a plurality of surfaces and configured to display arepresentation of a media file of an event in response to a firstsurface of the plurality of surfaces facing forward, to display firstdata of the event in response to a second surface of the plurality ofsurfaces facing forward, and to display second data of the event inresponse to a third surface of the plurality of surfaces facing forward;causing display of the 3D virtual display element; and activating amedia player to play the media file of the event outside the firstsurface based on the first surface facing forward.
 16. The system ofclaim 15, wherein the operations further comprise: configuring the 3Dvirtual display element to assign the representation of the media fileof the event to the first surface of the plurality of surfaces.
 17. Thesystem of claim 15, wherein the operations further comprise: configuringthe 3D virtual display element to assign the first data of the event tothe second surface of the plurality of surfaces.
 18. The system of claim15, wherein the operations further comprise: configuring the 3D virtualdisplay element to assign the second data of the event to the thirdsurface of the plurality of surfaces.
 19. The system of claim 15,wherein: the first surface facing forward faces a user viewing thedisplayed 3D virtual display element.
 20. The system of claim 15,wherein the operations further comprise: configuring the 3D virtualdisplay element to assign third data of the event to a fourth surface ofthe plurality of surfaces.